Add test GitHub workflow #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds a test-workflow that tests compiling
|
I have a 'release' workflow as well. But I want to test it on a fork, which I can only do once the repo is public. So adding the test workflow for now is nice. |
|
Looks good. But do we want to run the CI job for all pushes on feature branches? Or do we want to limit it to |
|
main and PRs only. Which is 99% of all commits. But yes, let me sharpen the rules there. But the only reason I see not to do this, is that it might eat EF's free runner minutes. But I just talked with Flam: They are hardly used and if it gets low, we will buy some more. So that is also fine. As long as the cache works, I think we should use it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a test-workflow that tests compiling